Flow of Control while Loading CUSP

This topic describes the flow of application control when the CUSP desktop is opened.

The Process Platform application page starts with cusp.htm as its initial page. Once the URL for the Process Platform site is typed in the browser, the default page loads the IFRAME inside it, which in turn contains the cusp.htm page. The OpenText Process Suite Platform User Start Page (CUSP) page shows all the tasks that the user has access to (based on the role).

When you open CUSP, thesystemcomponent is loaded. CUSP thus functions as the root for all applications. The CUSP body registers a frame, calledmain, in which all the applications are loaded.

This is followed by loading the Application UI, which is the container for applications; that is all applications are loaded inside Application UI. The container itself is surrounded by a set of GUI representations that handle all the GUI-related activities of an application's container. The common GUI-activities include maximize, minimize, show, and hide. Once the container is initialized, theguiRepresentationobject for containers is also initialized.

Requests are then sent to LDAP to retrieve user details. User details include the role and organizations that the user belongs to. These user details are authenticated and a request is sent to the XDS repository to retrieve content for the user. The retrieved content comprises assigned tasks, shortcuts, and automatic applications that are loaded and displayed in CUSP.

The applications loaded in CUSP are nothing but Web pages that the Process Platform Ajax Toolkit application framework can recognize and read. Once initialized, the default browser settings for CUSP are then retrieved from saved user preferences in the XDS Repository.